Custom Menus on the server

I do not know how to customize menus on the server, in part, because I do not have access to the server (IT Nazis). I've modified individual clients successfully in the {doorsHome}\lib\config and {doorsHome}\lib\config\baseWindowMenuFiles folders. But when I was shown that there is no \lib folder underneath DOORS on the server, I was not sure if they should create the directory structure or what. I cannot guess on this network.
MattatWSMR - Mon May 02 11:44:42 EDT 2011

Re: Custom Menus on the server
llandale - Mon May 02 15:54:54 EDT 2011

It looks like the Nazis have not installed the DOORS Client on the server. In any case, you cannot install menus on the server and expect them to be built in all the clients.

Perhaps you can indeed use the client on the Server and are expecting to be able to modify menus just for that client. If so, run Help >About to find out where your DOORS is actually installed.

But you say you have no access, yet you know the server has no such directories. Perhaps its a matter of access rights, the Nazis won't let you even see the install folders.

  • Louie

"Nazis" may be politically incorrect and you all know how much I care about that. How about "IT CatBerts", for Dilbert cartoon fans.

Re: Custom Menus on the server
MattatWSMR - Mon May 02 16:10:37 EDT 2011

llandale - Mon May 02 15:54:54 EDT 2011
It looks like the Nazis have not installed the DOORS Client on the server. In any case, you cannot install menus on the server and expect them to be built in all the clients.

Perhaps you can indeed use the client on the Server and are expecting to be able to modify menus just for that client. If so, run Help >About to find out where your DOORS is actually installed.

But you say you have no access, yet you know the server has no such directories. Perhaps its a matter of access rights, the Nazis won't let you even see the install folders.

  • Louie

"Nazis" may be politically incorrect and you all know how much I care about that. How about "IT CatBerts", for Dilbert cartoon fans.

The DOORS Client is NOT installed on the DOORS server right now. If that fixes the problem, I'll be happy.

I can control the DOORS menus on one client from one client. What I want is to install a global menu that all users/clients will see. Loading menu files on each individual client is cumbersome and a version nightmare. I assumed DOORS routinely handled this from the server.

We have IT people controlling the servers, so I normally have no access. They allowed me to get a glimpse of what they see - this time - to show me there was no \lib folder.

Re: Custom Menus on the server
MattatWSMR - Mon May 02 16:33:23 EDT 2011

MattatWSMR - Mon May 02 16:10:37 EDT 2011
The DOORS Client is NOT installed on the DOORS server right now. If that fixes the problem, I'll be happy.

I can control the DOORS menus on one client from one client. What I want is to install a global menu that all users/clients will see. Loading menu files on each individual client is cumbersome and a version nightmare. I assumed DOORS routinely handled this from the server.

We have IT people controlling the servers, so I normally have no access. They allowed me to get a glimpse of what they see - this time - to show me there was no \lib folder.

Actually, installing the client on the server is another problem because it would cost me another client license. DOORS is not cheap! In no other client/server software that I'm aware of (e.g. SQL Server), do you install the client software on the server as well.

Re: Custom Menus on the server
llandale - Mon May 02 16:40:54 EDT 2011

MattatWSMR - Mon May 02 16:10:37 EDT 2011
The DOORS Client is NOT installed on the DOORS server right now. If that fixes the problem, I'll be happy.

I can control the DOORS menus on one client from one client. What I want is to install a global menu that all users/clients will see. Loading menu files on each individual client is cumbersome and a version nightmare. I assumed DOORS routinely handled this from the server.

We have IT people controlling the servers, so I normally have no access. They allowed me to get a glimpse of what they see - this time - to show me there was no \lib folder.

No, you cannot install Menus on the Server and expect the Clients to see them. The DOORS Server software does very little. It gets requests for retrieval and update of values and it does so in the database. It has NOTHING to do with the DOORS GUI.

Yes, installing updated menus on each client ranges from "cumbersome" to "nightmare". I surely have never attempted to go there myself. Besides, evil IT departments won't let you modify the installation of an approved program anyway.

If you want to make custom DXL available to various users go the "addins" approach and leave the existing menus alone.

If you find a good way to do this you will get the gold star.

  • Louie

There are a bunch of folks whose opinion I respect here that disagree with me, and hopefully they will chime in.

Re: Custom Menus on the server
MattatWSMR - Mon May 02 16:48:04 EDT 2011

llandale - Mon May 02 16:40:54 EDT 2011
No, you cannot install Menus on the Server and expect the Clients to see them. The DOORS Server software does very little. It gets requests for retrieval and update of values and it does so in the database. It has NOTHING to do with the DOORS GUI.

Yes, installing updated menus on each client ranges from "cumbersome" to "nightmare". I surely have never attempted to go there myself. Besides, evil IT departments won't let you modify the installation of an approved program anyway.

If you want to make custom DXL available to various users go the "addins" approach and leave the existing menus alone.

If you find a good way to do this you will get the gold star.

  • Louie

There are a bunch of folks whose opinion I respect here that disagree with me, and hopefully they will chime in.

I'm really, REALLY disapointed with DOORS, but thanks for the information. I'll look at addins.

Yeah, our "evil IT department" does not like change.

Re: Custom Menus on the server
SystemAdmin - Wed May 04 08:18:40 EDT 2011

MattatWSMR - Mon May 02 16:48:04 EDT 2011
I'm really, REALLY disapointed with DOORS, but thanks for the information. I'll look at addins.

Yeah, our "evil IT department" does not like change.

....I'm really, REALLY disapointed with DOORS....

Don't be disappointed, it's just a case of knowing how, that's what this forum is for.

I just want to back-up louie's recommendation to use the DOORS "Addins" approach, this at least allows you to deliver dxl functions to multiple clients from a central location. The prime down side to this approach is the need to use a network share and that all DOORS users need to have Read access to this share (don't give them Write access, only you should have write access so that you can add, modify and generally have control over the the dxl being delivered. You'll need the IT guys to help you here - good luck! Perhaps go to them bearing gifts - pizza, cola and tickets to the latest sci-fi film has been known to work :-)

Look for the section named "Rational DOORS window control" in the DXL Reference manual, this is where you will find some basic patchy info about this method - use this forum to help fill in the gaps. IBM have also posted tech notes on this - click here.


Paul Miller
Melbourne, Australia

Re: Custom Menus on the server
SystemAdmin - Wed May 04 08:33:10 EDT 2011

MattatWSMR - Mon May 02 16:33:23 EDT 2011
Actually, installing the client on the server is another problem because it would cost me another client license. DOORS is not cheap! In no other client/server software that I'm aware of (e.g. SQL Server), do you install the client software on the server as well.

Installing the client software on the server won't actually solve this problem, but shouldn't cost you anything either. You only use a floating license when the client is in use, so installing is 'free', running the client is what consumes the license.

Re: Custom Menus on the server
MattatWSMR - Wed May 04 10:19:57 EDT 2011

SystemAdmin - Wed May 04 08:18:40 EDT 2011
....I'm really, REALLY disapointed with DOORS....

Don't be disappointed, it's just a case of knowing how, that's what this forum is for.

I just want to back-up louie's recommendation to use the DOORS "Addins" approach, this at least allows you to deliver dxl functions to multiple clients from a central location. The prime down side to this approach is the need to use a network share and that all DOORS users need to have Read access to this share (don't give them Write access, only you should have write access so that you can add, modify and generally have control over the the dxl being delivered. You'll need the IT guys to help you here - good luck! Perhaps go to them bearing gifts - pizza, cola and tickets to the latest sci-fi film has been known to work :-)

Look for the section named "Rational DOORS window control" in the DXL Reference manual, this is where you will find some basic patchy info about this method - use this forum to help fill in the gaps. IBM have also posted tech notes on this - click here.


Paul Miller
Melbourne, Australia

I've looked at the "Addins" approach and created a simple menu. But I believe this is for Module Menus and/or for adding to the DXL library. And it requires files and subfolders on the client (addins folder).

At the moment, I'm just interested in DOORS Explorer menus because my DXL scripts key off the current location and act on a few related modules in one folder. (We have many parallel folders with this module structure.) I now have an approach that will work for me, essentially what Paul suggests. I see the #include statement can refer to network shares, so I only need ONE file on each client (under baseWindowMenuFiles) that refers to the network share. I can modify the network share files from time to time. I even have it fine-tuned so that different users will see different menus.

Also, hazelw, I did not know that's how the client licenses work, so thanks for that. Thanks everybody (Louie, Paul, and hazelw) for the useful input. Oh, and Paul, the evil IT people here get their bribes higher up (I think). Sci-Fi would make a great bribe for me but I'm just a database manager/developer.

Re: Custom Menus on the server
MattatWSMR - Wed May 04 10:20:06 EDT 2011

SystemAdmin - Wed May 04 08:18:40 EDT 2011
....I'm really, REALLY disapointed with DOORS....

Don't be disappointed, it's just a case of knowing how, that's what this forum is for.

I just want to back-up louie's recommendation to use the DOORS "Addins" approach, this at least allows you to deliver dxl functions to multiple clients from a central location. The prime down side to this approach is the need to use a network share and that all DOORS users need to have Read access to this share (don't give them Write access, only you should have write access so that you can add, modify and generally have control over the the dxl being delivered. You'll need the IT guys to help you here - good luck! Perhaps go to them bearing gifts - pizza, cola and tickets to the latest sci-fi film has been known to work :-)

Look for the section named "Rational DOORS window control" in the DXL Reference manual, this is where you will find some basic patchy info about this method - use this forum to help fill in the gaps. IBM have also posted tech notes on this - click here.


Paul Miller
Melbourne, Australia

I've looked at the "Addins" approach and created a simple menu. But I believe this is for Module Menus and/or for adding to the DXL library. And it requires files and subfolders on the client (addins folder).

At the moment, I'm just interested in DOORS Explorer menus because my DXL scripts key off the current location and act on a few related modules in one folder. (We have many parallel folders with this module structure.) I now have an approach that will work for me, essentially what Paul suggests. I see the #include statement can refer to network shares, so I only need ONE file on each client (under baseWindowMenuFiles) that refers to the network share. I can modify the network share files from time to time. I even have it fine-tuned so that different users will see different menus.

Also, hazelw, I did not know that's how the client licenses work, so thanks for that. Thanks everybody (Louie, Paul, and hazelw) for the useful input. Oh, and Paul, the evil IT people here get their bribes higher up (I think). Sci-Fi would make a great bribe for me but I'm just a database manager/developer.

Re: Custom Menus on the server
llandale - Wed May 04 11:02:10 EDT 2011

MattatWSMR - Wed May 04 10:19:57 EDT 2011
I've looked at the "Addins" approach and created a simple menu. But I believe this is for Module Menus and/or for adding to the DXL library. And it requires files and subfolders on the client (addins folder).

At the moment, I'm just interested in DOORS Explorer menus because my DXL scripts key off the current location and act on a few related modules in one folder. (We have many parallel folders with this module structure.) I now have an approach that will work for me, essentially what Paul suggests. I see the #include statement can refer to network shares, so I only need ONE file on each client (under baseWindowMenuFiles) that refers to the network share. I can modify the network share files from time to time. I even have it fine-tuned so that different users will see different menus.

Also, hazelw, I did not know that's how the client licenses work, so thanks for that. Thanks everybody (Louie, Paul, and hazelw) for the useful input. Oh, and Paul, the evil IT people here get their bribes higher up (I think). Sci-Fi would make a great bribe for me but I'm just a database manager/developer.

You automatically get module "addins" in the user folder here:
c:\Program Files\IBM\Rational\DOORS\9.x\lib\dxl\addins\user.

If you define the variable "addins" you can get additional menus stored on some file server. Set up the file server hierarchy correctly, have doors folks use new DOORS icon target:

"c:\Program Files\IBM\Rational\DOORS\9.x\bin\doors.exe" -a "\\MyFileServer\DOORS\DXL\ModuleAddins".

To get DOORS database/project/folder scripts to appear in the Explorer (don't need an open module), use the "ProjectAddins" variable:

"c:\Program Files\IBM\Rational\DOORS\9.x\bin\doors.exe" -J "\\MyFileServer\DOORS\DXL\ProjectAddins".

See the other posts link to messages discussing that in more detail.

  • Louie

Digressing: I just realized why I called my target folder "\ProjectScripts" 12 or so years ago, its because the variable is "ProjectAddins". Maybe I should call the folder "\ExplorerScripts" with sibling folder "\ModuleScripts" ..err.. "\FormalScripts". With also sibling "\LinkModScripts".

Now the variable is called "ProjectAddins" because in DOORS v4; the explorer displayed only one Project at a time so that name made sense.